Delivery of Messages to A Reciever Mobile Device

ABSTRACT

A system for delivering messages to a receiver mobile device and a method and memory storing instructions therefor are described. The system comprises a key server arranged to: transmit a first signal responsive to receipt of a message from a sender mobile device; transmit a delivery confirmation notice responsive to receipt of a second signal from the receiver mobile device; transmit a key to the receiver mobile device responsive to receipt of the second signal from the receiver mobile device; and a message server communicatively coupled with the key server and arranged to: transmit a third signal to the receiver mobile device responsive to receipt of the first signal from the key server; transmit a fourth signal to the sender mobile device responsive to receipt of the delivery confirmation notice from the key server.

BACKGROUND

Many mobile devices are able to transmit messages, e.g., text and/ormultimedia messages, in addition to including the ability to communicatetelephonically, e.g., audible communication. Fees related totransmission of a message from a sender to a receiver are eitherincurred by the sender at the time of transmission initiation or at thetime of transmission reception by the receiver. Alternatively, feesrelated to transmission of the message may be negotiated to be paid bythe receiver in the form of the sender transmitting a first message tothe receiver requesting the receiver to accept fees related to a messageto be sent followed by transmission of the message to the receiver afterthe receiver accepts the fees.

DESCRIPTION OF THE DRAWINGS

One or more embodiments are illustrated by way of example, and not bylimitation, in the figures of the accompanying drawings, whereinelements having the same reference numeral designations represent likeelements throughout and wherein:

FIG. 1 is a high-level functional block diagram of a communicationsystem in conjunction with which an embodiment may be used to advantage;

FIG. 2 is a block diagram of a portion of a memory according to anembodiment;

FIG. 3 is a block diagram of a portion of another memory according to anembodiment;

FIG. 4 is a high-level process flow diagram of a key server messagehandler according to an embodiment;

FIG. 5 is a high-level process flow diagram of an encryption engineaccording to an embodiment;

FIG. 6 is a high-level process flow diagram of a message server messagehandler according to an embodiment;

FIG. 7 is a high-level message sequence diagram of a message flowaccording to an embodiment;

FIG. 8 is a block diagram of a message according to an embodiment;

FIG. 9 is a block diagram of an encrypted message according to anembodiment;

FIG. 10 is a block diagram of a message comprising a fee indicatoraccording to an embodiment;

FIG. 11 is a block diagram of an encrypted message comprising a feeindicator according to an embodiment; and

FIG. 12 is a high-level block diagram of a mobile device according to anembodiment.

DETAILED DESCRIPTION

FIG. 1 depicts a high-level functional block diagram of a communicationsystem 100 in conjunction with which an embodiment may be used toadvantage. Communication system 100 comprises a sender mobile device 102and a receiver mobile device 104 each communicatively coupled with awireless network 106. Wireless network 106 comprises a key server 108communicatively coupled with a message server 110, sender mobile device102, and receiver mobile device 104.

In accordance with an embodiment, sender mobile device 102 transmits amessage to receiver mobile device 104 wherein fees related totransmission of the message are incurred, based on an action of the userof the receiver mobile device, either by a user of receiver mobiledevice or by a user of the sender mobile device. The transmitted messagemay be referred to as a “collect message” as the sender is requestingthe receiver to pay for receipt of the message. If, after receipt of anencrypted form of the message from sender mobile device 102, receivermobile device 104 transmits a decryption key request to wireless network106, then fees associated with the message are assigned to the receivermobile device. If receiver mobile device 104 transmits a reject messageto wireless network 106, then fees associated with the message areassigned to sender mobile device 102.

Wireless network 106 is a communication network comprising wired and/orwireless connections for routing messages between two or morewireless-enabled mobile devices, e.g., mobile devices 102, 104. In atleast some embodiments, wireless network 106 transfers packets ofinformation, e.g., multimedia and/or text messages, between sendermobile device 102 and receiver mobile device 104.

Key server 108 and message server 110 are processing devices, such as acomputer system comprising a processor and/or an application specificintegrated circuit, which communicates with mobile devices 102, 104 inaccordance with a method of at least one embodiment. In at least someembodiments, key server 108 and message server 110 may comprise a singleprocessing device.

In at least some embodiments, key server 108 is an unstructuredsupplementary service data (USSD) server or similar device for providingsession-based communication with a mobile device. In at least someembodiments, message server 110 is a short message service (SMS) serverand/or a multimedia message service (MMS) server. In at least someembodiments, message server 110 is a wireless application platform(WAP)-based server.

Mobile devices 102, 104 are referred to as “sender” and “receiver” inorder to facilitate description of the embodiments herein. In at leastsome embodiments, mobile device 104 may be referred to as a sender andmobile device 102 may be referred to as a receiver.

In at least some embodiments, mobile devices 102, 104 are mobilecommunication devices such as wireless telephones, e.g., cellular mobiletelephones, personal digital assistants, etc. In at least someembodiments, mobile devices 102, 104 comprise functionality, e.g.,hardware, software, and/or firmware, enabling the devices to decryptencrypted messages received from message server 110 using a decryptionkey received from key server 108.

FIG. 2 depicts a block diagram of a portion of a memory 200 of keyserver 108 comprising a key server message handler 202, a key set 204,and an encryption engine 206.

Key server message handler 202 comprises a set of instructions which,when executed by a processor, cause the processor to perform a messagehandling functionality of key server 108 according to an embodiment. Keyset 204 comprises a set of encryption keys corresponding to one or moremessages handled by key server 108 executing key server message handler202. Encryption engine 206 comprises a set of instructions which, whenexecuted by a processor, cause the processor to perform an encryptionfunctionality of key server 108 according to an embodiment.

FIG. 3 depicts a block diagram of a portion of a memory 300 of messageserver 110 comprising a message server message handler 302. Messageserver message handler 302 comprises a set of instructions which, whenexecuted by a processor, cause the processor to perform a messagehandling functionality of message server 110 according to an embodiment.

In at least some embodiments, memories 200, 300 may comprise acomputer-readable medium such as a dynamic memory, a static memory, avolatile memory, a non-volatile memory, and/or a combination thereof. Inat least some embodiments, memories 200, 300 may comprise a randomaccess memory, a read only memory, a hard disk, a compact disc, adigital versatile disc, or another medium from which a processing devicemay read.

FIG. 4 depicts a high-level process flow diagram of at least a portionof a set of instructions comprising key server message handler 202according to an embodiment. The process flow begins at a receive messagefunctionality 400 wherein in response to receipt of a message, aprocessor of key server 108 executes a set of instructions causing theprocessor to receive a message.

During execution of receive message functionality 400, key servermessage handler 202 causes the processor to determine whether thereceived message is a collect message from sender mobile device 102 orreceiver mobile device 104.

In at least some embodiments, a user manipulates sender mobile device102 to cause the mobile device to transmit a selected message to keyserver 108. For example, in an embodiment, the user manipulates themobile device to input a prefix dialing instruction, such as “*123,” toinitiate a collect message request prior to entering the destinationaddress of the receiver and then composes and/or selects a previouslycomposed message for transmission. In at least some embodiments, theuser manipulates the mobile device to input a suffix dialing instructionto initiate a collect message request subsequent to entry of thedestination address. In at least some alternative embodiments, the usermanipulates one or more designated buttons on sender mobile device 102to initiate a collect message request.

In at least some alternative embodiments, the user manipulates themobile device to input a prefix dialing instruction followed by apredetermined destination address, e.g., a toll-free telephone numbersuch as a 1-800 number, and the destination address to which the messageis destined. The destination address is inserted by mobile device 102into the selected message, e.g., in a first set of digits, a last set ofdigits, etc., prior to transmission of the message to key server 108.

If the message is a collect message from sender mobile device 102requesting transmission, e.g., of a text and/or multimedia message, toreceiver mobile device 104, the flow proceeds to encrypt messagefunctionality 402 wherein execution of key server message handler 202 bythe processor causes the processor to encrypt at least a portion of thereceived message. In at least some embodiments, encrypt messagefunctionality 402 encrypts the message content. In at least some otherembodiments, encrypt message functionality 402 encrypts the receivedmessage except for the destination of the message.

In at least some other embodiments, encrypt message functionality 402encrypts a predetermined portion of the received message in order to,for example, permit a user of receiver mobile device 104 to preview anun-encrypted portion of the message content prior to obtaining the keyfor the message.

After at least a portion of the received message is encrypted, the flowproceeds to store key functionality 404 wherein the key server messagehandler 202 stores a decryption key, which is usable to decrypt at leastthe encrypted portion of the received message, in key set 204. The flowof control proceeds to forward encrypted message functionality 406,wherein the key server message handler 202 transmits the encryptedmessage to message server 110.

In at least some embodiments, a user manipulates receiver mobile device104 to cause the mobile device to transmit a key request message to keyserver 108. For example, in an embodiment, the user manipulates themobile device to input a dialing instruction, such as “*789,” toinitiate a key request message in response to receipt of the collectmessage to indicate acceptance of fees related to the collect message.In at least some embodiments, the user manipulates one or moredesignated buttons on receiver mobile device 104 to input a prefixdialing instruction prior to input of a predetermined address for thekey request message. In at least some alternative embodiments, the usermanipulates one or more designated buttons on receiver mobile device 104to initiate key request message.

Returning to receive message functionality 400, if the message is a keyrequest message from receiver mobile device 104, the flow proceeds toaccept/reject functionality 408 wherein the key server message handler202 determines whether the key request message requests a decryption keyfrom key server 108 to decrypt a received encrypted message. If thedetermination result of accept/reject functionality 408 is negative(“REJECT” or rejection message), receiver mobile device 104 hastransmitted a request key message indicating refusal of a user ofreceiver mobile device to incur fees related to the encrypted message. Anegative determination causes the flow to proceed to remove keyfunctionality 410 wherein the key server message handler 202 removes theencryption key associated with the encrypted message from key set 204.

The flow proceeds to send delivery confirmation notice functionality 412wherein the key server message handler 202 transmits a message, destinedfor sender mobile device 102 and comprising a delivery confirmationnotice, to message server 110. The transmitted delivery confirmationnotice comprises information indicating receipt of the message byreceiver mobile device 104 and refusal of the receiver mobile device 104to incur fees related to the message.

In at least some embodiments, the transmitted delivery confirmationnotice further comprises an indication that a fee related totransmission of the message from sender mobile device 102 to receivermobile device 104 is incurred by the user of the sender mobile device.In at least some embodiments, the fee incurred by the user of sendermobile device 102 due to refusal of the user of receiver mobile device104, is the fee which would have been incurred by the receiver mobiledevice user had the receiver mobile device user accepted the fee andrequested the decryption key. In at least some embodiments, the feeincurred by the user of sender mobile device 102 may be a predeterminedusage fee for transmitting a message to receiver mobile device 104 whichwas subsequently refused by the receiver mobile device user.

In an embodiment, if receiver mobile device 104 user refuses to incurfees related to the encrypted message, sender mobile device 102 incursthe fees related to transmission of the message and key server messagehandler 202 transmits the decryption key associated with the encryptedmessage to the receiver mobile device.

Returning to accept/reject functionality 408, if the determinationresult of accept/reject functionality 408 is positive (“ACCEPT” oracceptance message), receiver mobile device 104 has transmitted arequest key message indicating acceptance of a user of receiver mobiledevice to incur fees related to the encrypted message. A positivedetermination causes the flow to proceed to retrieve key functionality414 wherein the key server message handler 202 retrieves the encryptionkey associated with the encrypted message from key set 204.

In at least some embodiments, key server message handler 202 stores adecryption key in key set 204 based on a predetermined messageidentifier comprising a combination of an identifier of sender mobiledevice 102, an identifier of receiver mobile device 104, a messageidentifier, and/or a combination thereof. In at least some embodiments,the identifier may comprise a unique identifier such as a subscribernumber, device number, or other identifier. In this manner, anacceptance and/or a rejection message comprising the predeterminedmessage identifier may be used to determine the corresponding decryptionkey of key set 204 which is needed to decrypt the message.

The flow proceeds to transmit key functionality 416 wherein the keyserver message handler 202 (FIG. 2, key server 108) transmits therequested key to receiver mobile device 104. In at least someembodiments, transmit key functionality 416 further comprises remove keyfunctionality 410 in order to cause the key server message handler 202to remove the decryption key from key set 204 after retrieval of thekey.

The flow proceeds to send delivery confirmation notice functionality 412wherein the key server message handler 202 transmits a message, destinedfor sender mobile device 102 and comprising a delivery confirmationnotice, to message server 110. The transmitted delivery confirmationnotice comprises information indicating receipt of the message byreceiver mobile device 104 and acceptance of the receiver mobile device104 to incur fees related to the message.

FIG. 5 depicts a high-level process flow diagram of at least a portionof a set of instructions comprising encryption engine 206 according toan embodiment. The process flow begins at a receive messagefunctionality 500 wherein encryption engine 206 receives a messagecomprising at least a portion which is to be encrypted. For example, keyserver message handler 202 may invoke encryption engine 206 at encryptmessage functionality 402. The process flow proceeds to encrypt messagefunctionality 502 wherein the encryption engine encrypts at least aportion of the received message.

In at least some embodiments, encryption engine 206 may perform theencryption using an encryption method such as a public-private key pairbased method, a hash method, etc. In at least some embodiments,encryption engine 206 uses an encryption method determined by wirelessnetwork 106. In at least some other embodiments, encryption engine 206uses an encryption method determined by sender mobile device 102.

The flow of control proceeds to forward functionality 504 whereinencryption engine 206 transmits the encrypted portion of the receivedmessage and a decryption key to key server message handler 202. In atleast some embodiments, encryption engine 206 transmits the encryptedportion of the received message and stores the decryption key in key set204.

FIG. 6 depicts a high-level process flow diagram of at least a portionof a set of instructions comprising message server message handler 302according to an embodiment. The process flow begins at node 600 andbased on a signal received by the message server 110, the flow proceedsto receive encrypted message 602 or receive delivery confirmation notice604.

During receive encrypted message 602, message server message handler 302receives the encrypted message from key server 108. The flow proceeds toforward encrypted message 606 wherein message server message handler 302causes message server 110 to transmit the encrypted message to receivermobile device 104. In at least some embodiments, if the specifieddestination address, i.e., receiver mobile device 104, is not reachableby wireless network 106, message server 110 may store the encryptedmessage in memory 300 until the receiver mobile device becomes availableat which time the message server transmits the encrypted message to thereceiver mobile device.

During receive delivery confirmation notice 604, message server messagehandler 302 receives the delivery confirmation notice from key server108. The flow proceeds to forward delivery confirmation noticefunctionality 608 wherein message server message handler 302 causesmessage server 110 to transmit the delivery confirmation notice tosender mobile device 102.

In at least some embodiments, message server message handler 302 maygenerate and transmit a delivery confirmation notice to sender mobiledevice 102 based on a timer reaching a predetermined timeout value. Theflow of control proceeds from node 600 to timeout functionality 610after a timer reaches the predetermined timeout value. In at least someembodiments, the timer is set during execution of forward encryptedmessage functionality 606. After the timer reaches the predeterminedtimeout value, the flow proceeds to functionality 612 wherein themessage server 110 generates and transmits a delivery confirmationnotice to sender mobile device 102. In at least some embodiments, duringfunctionality 612, message server 110 also indicates acceptance of a feerelated to transmission of the collect message by sender mobile device102. That is, message server 110 causes sender mobile device 102 to becharged for the transmitted collect message.

For example, if a predetermined time has elapsed subsequent totransmission of the encrypted message to receiver mobile device withoutreceipt of a key request message by key server 108, i.e., message servermessage handler 302 has not received a delivery confirmation notice fromkey server message handler 202, then the message server message handlermay indicate that sender mobile device 102 has incurred a fee related totransmission of the message.

FIG. 7 depicts a message sequence diagram of a portion of interactionsbetween sender mobile device 102, key server 108, message server 110,and receiver mobile device 104 according to an embodiment. Time proceedsdownward along the page.

Sender mobile device 102 transmits a message destined for receivermobile device 104 to key server 108 (sequence 700). Key server 108,responsive to receipt of the message (FIG. 4 receive messagefunctionality 400), encrypts at least a portion of the message (FIG. 4encrypt message 402) and transmits the encrypted message (sequence 702)to message server 110.

Message server 110, responsive to receipt of the encrypted message,transmits the encrypted message to receiver mobile device 104 (sequence704). After receipt of the encrypted message by receiver mobile device104, the user of the receiver mobile device determines whether to acceptthe fee associated with obtaining the decryption key related to theencrypted message.

If the user accepts the fee, the user causes receiver mobile device 104to transmit a key request message to key server 108 wherein the keyrequest message indicates acceptance of the fee and requests the keyassociated with the received encrypted message (sequence 706). If theuser rejects the fee, the user causes receiver mobile device 104 totransmit a key request message to key server 108 wherein the key requestmessage indicates refusal of the fee (sequence 706).

If the key request message received by key server 108 indicatesacceptance of the fee and/or a request for the decryption keycorresponding to the encrypted message, the key server transmits thedecryption key to receiver mobile device 104 (sequence 708) afterretrieval from key set 204. If the key request message indicates refusalof the fee and/or no request for the decryption key, the key server doesnot transmit the decryption key to receiver mobile device 104.

After receipt of the key request message, key server 108 transmits thedelivery confirmation notice to message server 110 (sequence 710). Ifthe user accepted the fee, the delivery confirmation notice indicatesreceipt of the encrypted message and acceptance of the fee by the user.If the user refused the fee, the delivery confirmation notice indicatesreceipt of the encrypted message and refusal of the fee by the receivermobile device user.

After receipt of the delivery confirmation notice, message server 110transmits the delivery confirmation notice to sender mobile device 102.

FIG. 8 depicts a high-level block diagram of a message 800 transmittedby sender mobile device 102, i.e., a collect message. Collect message800 comprises a source address 802 specifying the sender mobile device102, a destination address 804 specifying the receiver mobile device104, and one or more pieces of content 806 such as a text message, amultimedia message, etc.

FIG. 9 depicts a high-level block diagram of a collect message 900similar to collect message 800 and comprising source address 802 anddestination address 804. Collect message 900, also referred to as anencrypted message, further comprises one or more pieces of encryptedcontent 902. Encrypted message 900 is transmitted from key server 108 tothe specified destination address 804, i.e., receiver mobile device 104,via message server 110. In at least some embodiments, collect message900 is transmitted from sender mobile device 102 to key server 108.

FIG. 10 depicts a high-level block diagram of a collect message 1000similar to collect message 800 and comprising source address 802 anddestination address 804. Collect message 1000 further comprises a feeindicator 1002 specifying a fee which the receiver agrees to pay inorder to receive the decryption key from key server 108. In at leastsome embodiments, collect message 1000 is transmitted from sender mobiledevice 102 to key server 108.

FIG. 11 depicts a high-level block diagram of a collect message 1100similar to collect message 900 and comprising source address 802 anddestination address 804. Collect message 1100, also referred to as anencrypted message, further comprises one or more pieces of encryptedcontent 902 and a fee indicator 1002. In at least some embodiments,encrypted message 1100 is transmitted from key server 108 to thespecified destination address 804, i.e., receiver mobile device 104, viamessage server 110. In at least some embodiments, encrypted message 1100is transmitted from sender mobile device 102 to key server 108.

In at least some embodiments, messages 800, 900, 1000, and 1100 lacksource address 802 which may, instead, be tracked by wireless network106.

In at least one alternative embodiment, sender mobile device 102transmits a collect message in the form of encrypted message 900 orencrypted message 1100 to key server 108. That is, sender mobile device102 encrypts content 806 prior to transmitting the collect message tokey server 108. In at least some embodiments, the encrypted content 902portion of the encrypted message is encrypted using a shared secretknown to key server 108. In at least some embodiments, the encryptedcontent 902 portion is encrypted using an encryption method known to keyserver 108 or an encryption method having a known decryption method orkey known to key server 108. In a still further embodiment, sendermobile device 102 transmits the decryption key to key server 108. Insome embodiments, sender mobile device 102 transmits the decryption keyas part of the encrypted message and in other embodiments, the sendermobile device transmits the decryption key in a separate message to keyserver 108. In at least some embodiments, the encryption key is thedecryption key and may be referred to as “key.”

FIG. 12 depicts a high-level functional block diagram of receiver mobiledevice 104 comprising a processor 1202, a memory 1204, a transceiver1206, and a user interface device 1208. Receiver mobile device 104further comprises a bus 1210 communicatively coupling processor 1202,memory 1204, transceiver 1206, and user interface (UI) device 1208.Processor 1202 executes a set of instructions read from memory 1204.Processor 1202 also causes transceiver 1206 to send and/or receive awireless signal from communication network 106. In at least someembodiments, transceiver comprises a receiver device and a transmitterdevice. Processor 1202 also receives input commands and information froma user via user interface device 1208 and provides information andoutput to the user via the user interface device, e.g., via a display, akeypad, a touch screen, a speaker, and/or a microphone.

Memory 1204 comprises data, e.g., a received encrypted message 1212, adecryption key 1214, and a decrypted message 1216 such as a decryptedversion of the received encrypted message, and one or more sets ofinstructions which may be read and executed by processor 1202 in orderto provide one or more functions of receiver mobile device 104. The setsof instructions stored in memory 1204 comprise a receive messagefunctionality 1218, a display message portion functionality 1220, agenerate key request functionality 1222, a receive key functionality1224, a decrypt message functionality 1226, and a remove messagefunctionality 1228.

Execution of receive message functionality 1218 by processor 1202 causesthe mobile device 104 to receive a message, e.g., an encrypted message1212 or comprised by a portion thereof, via communication network 106.In at least some embodiments, the message and/or the encrypted message1212 comprises an identifier identifying the encrypted message. In atleast some embodiments, key server 108 may uniquely identify theencrypted message and corresponding decryption key 1214 by use of one ormore of a message identifier, a receiver mobile device 104 identifier,and/or a sender mobile device identifier 102.

Execution of display message portion 1220 by processor 1202 causesmobile device 104 to display at least a portion of the receivedencrypted message 1212, e.g., a sender address, a subject line, anon-encrypted portion of the message, etc., to the user via UI device1208. Further, display message portion functionality 1220 is arranged tocause UI device 1208 to display one or both of decryption key 1214 anddecrypted message 1216 to the user. In at least some embodiments,display message portion functionality 1220 comprises instructions tocause UI device 1208 to display a user interface requesting the user toindicate whether to accept or reject a collect message.

Execution of generate key request functionality 1222 by processor 1202causes mobile device 104 to create and transmit a key request message(sequence 706 of FIG. 7) to key server 108. The key request message maycomprise an acceptance message or a rejection message. In at least someembodiments, generate key request functionality 1222 comprisesinstructions to cause UI device 1208 to display a user interfacerequesting the user to indicate whether to accept or reject a collectmessage. In at least some embodiments, display message portionfunctionality 1220 comprises instructions to cause UI device 1208 todisplay a user interface requesting the user to indicate whether toaccept or reject a collect message. In at least some embodiments,generate key request functionality 1222, during execution by processor1202, causes the transmitted key request message to comprise anidentifier identifying the encrypted message 1212. The transmitted keyrequest message may further comprise an identifier such as the addressand/or telephone number of mobile device 104 to aid in identifying theencrypted message 1212 by key server 108.

Execution of receive key functionality 1224 by processor 1202 causesmobile device 104 to receive decryption key 1214 via communicationnetwork 106. In at least some embodiments, decryption key 1214 comprisesan identifier identifying the encrypted message 1212 to which the keycorresponds and which may be decrypted using the key. Receive keyfunctionality 1224 is also arranged to cause processor 1202 to store thereceived decryption key 1214 in memory 1204. In at least someembodiments, decryption key 1214 comprises a message identifieridentifying the encrypted message 1212 to which the decryption keycorresponds.

Execution of decrypt message functionality 1226 by processor 1202 causesmobile device 104 to decrypt encrypted message 1212 using decryption key1214. In at least some embodiments, decrypt message functionality 1226may cause execution of display message portion 1220 to display thedecrypted message to the user via UI device 1208.

Execution of optional remove message functionality 1228 by processor1202 causes mobile device 104 to remove, e.g., to delete or otherwiseremove from memory 1204 and/or remove references to, one or more ofencrypted message 1212, decryption key 1214, and decrypted message 1216.In at least some embodiments, remove message functionality 1228 isarranged to execute to remove the encrypted message 1212 in response toone or more of a user input received at UI device 1208 and a signal fromkey server 108. In at least some embodiments, encrypted message 1212,decryption key 1214, and/or decrypted message 1216 may comprise anexpiration time after which remove message functionality 1228 executesto remove the message and/or key from memory. In at least someembodiments, creation of and/or transmission of a key request messagecomprising a rejection message may cause execution of remove messagefunctionality 1228 with respect to the rejected message.

1. A system for delivering messages to a receiver mobile device,comprising: a key server arranged to: transmit a first signal responsiveto receipt of a message from a sender mobile device; transmit a deliveryconfirmation notice responsive to receipt of a second signal from thereceiver mobile device; transmit a key to the receiver mobile deviceresponsive to receipt of the second signal from the receiver mobiledevice; and a message server communicatively coupled with the key serverand arranged to: transmit a third signal to the receiver mobile deviceresponsive to receipt of the first signal from the key server; transmita fourth signal to the sender mobile device responsive to receipt of thedelivery confirmation notice from the key server.
 2. The system of claim1, wherein the first signal comprises an encrypted message.
 3. Thesystem of claim 1, wherein the message received from the sender mobiledevice comprises an encrypted message.
 4. The system of claim 3, whereinthe message received from the sender mobile device further comprises akey related to the encrypted message.
 5. The system of claim 1, whereinthe key server is further arranged to receive a key signal from thesender mobile device, wherein the key signal comprises a key related tothe encrypted message.
 6. The system of claim 1, wherein the secondsignal comprises at least one of a key request message and a rejectionmessage.
 7. The system of claim 1, wherein the third signal comprises anencrypted message.
 8. The system of claim 1, wherein the deliveryconfirmation notice comprises at least one of an acceptance message anda rejection message.
 9. The system of claim 1, wherein the fourth signalcomprises the delivery confirmation notice.
 10. The system of claim 9,wherein the delivery confirmation notice comprises at least one of anacceptance message and a rejection message.
 11. The system of claim 1,wherein the third signal comprises a fee indicator specifying a feechargeable to the receiver mobile device.
 12. The system of claim 1,wherein the message server is further arranged to indicate a feeincurred by the receiver mobile device responsive to the deliveryconfirmation notice comprising an acceptance message.
 13. The system ofclaim 1, wherein the message server is further arranged to indicate afee incurred by the sender mobile device responsive to the deliveryconfirmation notice comprising a rejection message.
 14. A method ofdelivering messages to a receiver mobile device, comprising:transmitting a collect message to a receiver mobile device, wherein thecollect message comprises encrypted content; and indicating acceptanceof a fee by at least one of: the receiver mobile device responsive toreceipt of an acceptance message from the receiver mobile device; and asender mobile device responsive to receipt of a rejection message fromthe receiver mobile device.
 15. The method of claim 14, wherein theindicating acceptance of a fee further comprises indicating acceptanceof a fee by the sender mobile device responsive to a predeterminedtimeout period.
 16. The method of claim 14, further comprising:transmitting a key to the receiver mobile device responsive to receiptof the acceptance message from the receiver mobile device, wherein thekey corresponds to the encrypted content.
 17. The method of claim 14,further comprising: transmitting a delivery confirmation notice to thesender mobile device responsive to receipt of at least one of theacceptance message and the rejection message.
 18. A mobile devicearranged to receive a collect message, comprising: a processor; areceiver device communicatively coupled to the processor; and a memorycommunicatively coupled to the processor and arranged to store a set ofinstructions which, when executed by the processor, cause the processorto: store in the memory at least a portion of a collect message receivedvia the receiver device wherein the collect message comprises anencrypted portion; receive a key request indication from a user based ondisplay of an un-encrypted portion of the collect message, wherein thekey request indication comprises at least one of an acceptanceindication and a rejection indication.
 19. The mobile device of claim18, further comprising: a transmitter device communicatively coupled tothe processor, and wherein the memory further comprises a set ofinstructions arranged to cause the processor to: transmit, subsequent toreceipt of the key request indication, a key request message using thetransmitter device wherein the key request message comprises at leastone of an acceptance message and a rejection message based on thereceived key request indication.
 20. The mobile device of claim 19,wherein the memory further comprises a set of instructions arranged tocause the processor to: receive a decryption key in response to thetransmitted key request message, wherein the decryption key correspondsto at least the encrypted portion of the collect message; and decrypt atleast the encrypted portion of the collect message based on thedecryption key.